Put every CHANGELOG.md release header in the `## KiteViewers vX.Y.Z YYYY-MM-DD` form and fold the stale 2024 `## Unreleased` into v0.4.20 by 1-Bort-1 · Pull Request #59 · OpenSourceAWE/KiteViewers.jl

1-Bort-1 · 2026-10-06T12:10:21Z

Every release header now reads ## KiteViewers vX.Y.Z YYYY-MM-DD, which is the form the release bump writes (1-Bart-1/Agents#635). Pending notes now have one place to go: the single ## Unreleased at the top of the file. That section currently holds the Julia 1.12/1.13 note from #61.

An old ## Unreleased from 2024 sat between v0.4.14 and v0.4.13, so the next release would have been written there instead of above v0.6.0. Its notes shipped in v0.4.20 under the wrong heading. Uwe wrote them on 2024-11-02, the same day he added examples/reelout_1p.jl, and v0.4.20 (2024-11-09) is the first tag that contains that example. The three notes now sit under v0.4.20's ### Changed. I dropped the fourth, "add example reelout_1p.jl", because v0.4.20's ### Added already has it word for word.

Other header fixes: v 0.5.2 becomes v0.5.2, and the - before each date is gone. v0.4.24 was dated 2025-01-06, but its tag and GitHub release are both dated 2025-06-01, so the day and month had been swapped. ### Changes becomes ### Changed, and v0.4.16's one bugfix line, which had no heading, now sits under ### Fixed. Only headings changed: a note filed under the wrong category stays where it is, and no note text was reworded.

0.6.1 was never released. Project.toml on main says 0.6.0, the same version as the latest tag, GitHub release and top release header. No commit has ever set 0.6.1.

CLAUDE.md told contributors to add notes under ## Unreleased until the version is bumped, which is how the stale section came about. It now points them at changelog.d/<issue>-<slug>.md and names the release header form.

Verification

Reproduced first: the box's bump (withRelease) on the old main CHANGELOG put ## KiteViewers v0.6.1 at line 135, between v0.4.14 and v0.4.13. On this branch it goes at the top.
Every ## line except the one ## Unreleased matches ^## KiteViewers v[0-9.]+ [0-9]{4}-[0-9]{2}-[0-9]{2}$, and every ### heading is Added, Fixed or Changed. I checked both with grep.
Release rehearsal. I copied the head to a scratch checkout, renamed ## Unreleased to ## KiteViewers v0.6.1 2026-10-11 and set the version to 0.6.1, as a bump would. On that commit the box's bin/release --dry-run passes the version check and the release-notes check. It then stops at "commit not found on GitHub", which is the next check and expected for a commit that was never pushed. On the head itself it refuses at ## Unreleased, exactly as it does on main, because it is meant to run on the bump commit.
Up to date with main (merged ae9b8d9). Conflict resolution: I kept main's new ## Unreleased note and this branch's ISO header for v0.6.0.
Local full suite (Julia 1.13, one matrix cell) started on the merge commit · GitHub CI pending. The resolution touches only markdown.
Risk: the v0.4.24 date and the fold into v0.4.20 come from tags and commit dates, not from Uwe, so he should confirm both.

Opened by 1-Bort-1, an AI agent working for @1-Bart-1.
Closes #58 · task KiteViewers.jl-58

Release headers become '## KiteViewers vX.Y.Z YYYY-MM-DD', '### Changes' becomes '### Changed', v0.4.24 carries its tag date, and the stale 2024 '## Unreleased' is folded into v0.4.20, the first release that shipped it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1

Independent review (advisory)

Verdict: APPROVE WITH COMMENTS · 0 inline, 0 off the diff

Good

All 22 ## lines now match ## KiteViewers vX.Y.Z YYYY-MM-DD and every ### heading is Added, Fixed or Changed; I checked this with a grep of the branch's CHANGELOG.md.
The v0.4.24 date fix (2025-01-06 → 2025-06-01) is correct: git tag gives the v0.4.24 creator date as 2025-06-01, and the v0.4.20–v0.4.23 dates also match their tags.
Removing the stray ## Unreleased fixes the real defect in issue #58, since a release tool inserting above the first ## Unreleased would have put the next release between v0.4.14 and v0.4.13.
bin/release still works: its awk keys on /^## KiteViewers / and takes $3 as the version, and dropping - before the date does not move the third field.
Dropping the duplicate 'add example reelout_1p.jl' line is right, because v0.4.20 ### Added already has the same line.
Scope stays where the card says: headers only, no note text reworded, and the missing bin/install (#55) changelog note is named as left out instead of hidden.

Not good

CLAUDE.md:117-118 still tells contributors that 'new entries go under ## Unreleased until the version in Project.toml is bumped'. That is the instruction that created the stray section, and the next agent that follows it will add a new ## Unreleased and bring the bug back. It is close to this change and should be updated to the changelog.d/ convention in this PR or a linked follow-up.
PlanV3.md:150 likewise tells the reader to file entries under ## Unreleased. It is a stale plan file that probably should not be tracked at all (rubric §9).
Moving the three orphaned lines under v0.4.20 relies on commit dates and tag contents, not on the author. The evidence is sound, but the release notes now credit v0.4.20 with changes such as 'improve installation instructions' that nobody listed at the time. That is acceptable, but Uwe should confirm it as well as the v0.4.24 date.
v0.4.13 and v0.5.2 keep fixes ('fix tests', 'fix examples', 'fix pre-compilation') under ### Changed. That is fine for a headers-only PR, but the card's claim that every section now has a correct category is only true of the heading names, not of what is filed under them.

_{claude, rubric CLEAN_CODE.md. A different lab from the implementer

on purpose: a reviewer sharing its blind spots would not flag its mistakes.}

…er form Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1 · 2026-10-06T12:22:10Z

Local full suite: PASS (1 min, Julia 1.13.0, one cell of the matrix)

codecov-commenter · 2026-10-06T12:34:40Z

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

1-Bort-1 · 2026-10-06T12:59:44Z

CLAUDE.md: fixed in 14e0cca, its changelog rule now points at changelog.d/ and the release header form. PlanV3.md:150: left alone, since one ## Unreleased above every release is still a valid convention and whether the plan stays tracked is Uwe's call. v0.4.20 fold and v0.4.24 date: agreed, and the card's Risk line now asks Uwe to confirm both. Fixes filed under ### Changed: agreed, it was heading names only, and the card now says so.

1-Bort-1 · 2026-10-09T11:01:49Z

From Agents-635 (1-Bart-1/Agents#635)

Per 1-Bart-1/Agents#635: since 1-Bart-1/Agents#634 the release bump writes headers as ## <Package> vX.Y.Z DD-MM-YYYY. Please switch every release header this branch writes from ISO YYYY-MM-DD to DD-MM-YYYY (e.g. 2026-09-28 → 28-09-2026), and rewrite the title and description to match. Keep date-released in CITATION.cff ISO, as the CFF schema requires.

Per 1-Bart-1/Agents#634 the release bump writes ## <Package> vX.Y.Z DD-MM-YYYY. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1 · 2026-10-10T15:23:53Z

From Agents-635 (1-Bart-1/Agents#635)

Per 1-Bart-1/Agents#635 (comment 6099024080) ISO is the convention after all: the bump goes back to writing ## <Package> vX.Y.Z YYYY-MM-DD. Please put every release header this branch writes back to ISO YYYY-MM-DD (e.g. 28-09-2026 → 2026-09-28), including any already in the base it carries, and rewrite the title and description to match. date-released in CITATION.cff stays ISO. Sorry for the round trip.

Undoes 16f4573: per 1-Bart-1/Agents#635 the release bump writes ## <Package> vX.Y.Z YYYY-MM-DD again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1 · 2026-10-10T15:26:00Z

Reverted in 7b06463: every CHANGELOG.md header and CLAUDE.md's header form are ISO YYYY-MM-DD again (main carries none to convert); title and description rewritten. No CITATION.cff in this repo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

ufechner7 · 2026-10-11T18:36:18Z

The PR is invalid.

1-Bort-1 · 2026-10-11T18:38:37Z

Agreed, #59 stays closed. Nothing new is pushed and no replacement PR opens.

1-Bort-1 added agent:running Agent task state agent:ci Agent task state and removed agent:running Agent task state labels Oct 6, 2026

1-Bort-1 commented Oct 6, 2026

View reviewed changes

1-Bort-1 added agent:queued Agent task state agent:running Agent task state and removed agent:ci Agent task state agent:queued Agent task state labels Oct 6, 2026

Point CLAUDE.md's changelog rule at changelog.d/ and the release head…

14e0cca

…er form Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1 added agent:queued Agent task state agent:running Agent task state and removed agent:running Agent task state agent:queued Agent task state labels Oct 6, 2026

1-Bort-1 mentioned this pull request Oct 6, 2026

Bring KiteViewers' changelog to the release convention #58

Closed

1-Bort-1 added agent:ci Agent task state and removed agent:running Agent task state labels Oct 6, 2026

1-Bort-1 marked this pull request as ready for review October 6, 2026 13:00

1-Bort-1 added agent:review Agent task state and removed agent:ci Agent task state labels Oct 6, 2026

1-Bort-1 requested a review from 1-Bart-1 October 6, 2026 13:02

1-Bort-1 added agent:queued Agent task state agent:running Agent task state and removed agent:review Agent task state agent:queued Agent task state labels Oct 9, 2026

docs: write release header dates as DD-MM-YYYY

16f4573

Per 1-Bart-1/Agents#634 the release bump writes ## <Package> vX.Y.Z DD-MM-YYYY. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1 added agent:ci Agent task state agent:review Agent task state and removed agent:running Agent task state agent:ci Agent task state labels Oct 9, 2026

1-Bort-1 added agent:queued Agent task state agent:running Agent task state and removed agent:review Agent task state agent:queued Agent task state labels Oct 10, 2026

revert: write release header dates as ISO YYYY-MM-DD again

7b06463

Undoes 16f4573: per 1-Bart-1/Agents#635 the release bump writes ## <Package> vX.Y.Z YYYY-MM-DD again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1 added agent:ci Agent task state agent:review Agent task state agent:queued Agent task state agent:running Agent task state and removed agent:running Agent task state agent:ci Agent task state agent:review Agent task state agent:queued Agent task state labels Oct 10, 2026

merge: latest main

4909f8b

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

1-Bort-1 added agent:ci Agent task state agent:review Agent task state and removed agent:running Agent task state agent:ci Agent task state labels Oct 11, 2026

ufechner7 closed this Oct 11, 2026

Navigation Menu

Repository navigation

Put every CHANGELOG.md release header in the `## KiteViewers vX.Y.Z YYYY-MM-DD` form and fold the stale 2024 `## Unreleased` into v0.4.20 - #59

Put every CHANGELOG.md release header in the `## KiteViewers vX.Y.Z YYYY-MM-DD` form and fold the stale 2024 `## Unreleased` into v0.4.20#59
1-Bort-1 wants to merge 5 commits into
mainfrom
agent/58-bring-kiteviewers-changelog-to-the-relea

1-Bort-1 commented Oct 6, 2026 •

edited

Loading

Uh oh!

1-Bort-1 left a comment

Uh oh!

1-Bort-1 commented Oct 6, 2026 •

edited

Loading

Uh oh!

codecov-commenter commented Oct 6, 2026

Uh oh!

1-Bort-1 commented Oct 6, 2026

Uh oh!

1-Bort-1 commented Oct 9, 2026

Uh oh!

1-Bort-1 commented Oct 10, 2026

Uh oh!

1-Bort-1 commented Oct 10, 2026

Uh oh!

ufechner7 commented Oct 11, 2026

Uh oh!

1-Bort-1 commented Oct 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

1-Bort-1 commented Oct 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Verification

Uh oh!

1-Bort-1 left a comment

Choose a reason for hiding this comment

Independent review (advisory)

Uh oh!

1-Bort-1 commented Oct 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov-commenter commented Oct 6, 2026

Codecov Report

Uh oh!

1-Bort-1 commented Oct 6, 2026

Uh oh!

1-Bort-1 commented Oct 9, 2026

Uh oh!

1-Bort-1 commented Oct 10, 2026

Uh oh!

1-Bort-1 commented Oct 10, 2026

Uh oh!

ufechner7 commented Oct 11, 2026

Uh oh!

1-Bort-1 commented Oct 11, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

1-Bort-1 commented Oct 6, 2026 •

edited

Loading

1-Bort-1 commented Oct 6, 2026 •

edited

Loading